docs: Enterprise Use Case Tutorial - User Management, Access Controls, and Auditing with Feature Flags #8998
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Files |
website/docs/feature-flag-tutorials/use-cases/user-management-access-controls.md
Outdated
Show resolved
Hide resolved
website/docs/feature-flag-tutorials/use-cases/user-management-access-controls.md
Outdated
Show resolved
Hide resolved
website/docs/feature-flag-tutorials/use-cases/user-management-access-controls.md
Outdated
Show resolved
Hide resolved
website/docs/feature-flag-tutorials/use-cases/user-management-access-controls.md
Outdated
Show resolved
Hide resolved
| 1. Owner | ||
| 2. Member | ||
|
|
||
| Assign users with root roles to configure entire systems. These users can perform any operation within the Unleash platform and change permissions for other users when they belong to a specific user group. |
There was a problem hiding this comment.
I don't understand this sentence when paired with the fact that there are Admin, Editor and Viewer root roles. It would seem that a Viewer with a Root role wouldn't be able to "erform any operation within the Unleash platform and change permissions for other users when they belong to a specific user group." Can you clarify if this is for all root roles, or just admin? Also, if just for Admin, what does root role mean for Editor or Viewer? My guess is that they would have that level of access for all projects across the entire Unleash instance, not project by project but we should verify and clarify this point.
| - **Four-eyes approval workflows**: Multi-stage approval processes ensure critical changes are thoroughly reviewed and approved by at least 2 other people before implementation. | ||
| - **Compliance requirements**: For regulated industries like finance and healthcare, Change Requests provide the detailed documentation necessary to meet strict compliance standards. | ||
|
|
||
|  |
There was a problem hiding this comment.
This sentence is hard to parse. Can you revisit it please?
website/docs/feature-flag-tutorials/use-cases/user-management-access-controls.md
Outdated
Show resolved
Hide resolved
website/docs/feature-flag-tutorials/use-cases/user-management-access-controls.md
Outdated
Show resolved
Hide resolved
| 4. Final sign-off from technical leadership | ||
|
|
||
|  | ||
|
|
There was a problem hiding this comment.
I would like to add a link to Mateusz's blog on this topic. https://www.getunleash.io/blog/feature-flag-change-requests-how-to
Something like "For more detail on what enterprise-level change requests should include read our blog
|
|
||
| The most advanced implementations integrate Unleash audit logs directly into broader Security Information and Event Management (SIEM) systems. This enables real-time monitoring and creates a holistic view of system interactions across multiple platforms. By correlating Unleash audit data with other enterprise security logs, organizations can detect subtle patterns and potential security anomalies that might go unnoticed in isolated systems. | ||
|
|
||
| By implementing intelligent, automated, and granular access controls, organizations can create a secure foundation for continuous delivery at scale. |
There was a problem hiding this comment.
This conclusion sentence seems out of place. Only refers to access controls, not the rest of the topics in the blog.
Co-authored-by: Michael Ferranti <[email protected]>
About the changes
We're adding a new enterprise use case tutorial on user management, access controls, and auditing with feature flags.
All updates in this PR are changes made post-review of the Google Doc.
Closes #
Important files
Discussion points